-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add automated build workflow for Android #1656
Conversation
This is awesome! |
c65094b
to
a4107c8
Compare
@micahmo This is ready to be reviewed - if you could, please look over the workflow and let me know if there's something that I might be missing here as I'm not too familiar with GitHub actions/workflows! I've also updated the PR description to provide a bit more details. |
I'm not sure if it helps at all, but remember that you can upload secrets to the repository (Settings > Secrets and variables > Actions) which can be consumed in the actions. Maybe that will help to reuse existing certificates and such? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! I'm sure it will really help to simplify your process!
I'm doing this for the Android secrets! However, for iOS, there are a few certificates that are automatically managed by Xcode. This means that I would have to re-create those certificates and replace them first before I can add them into GitHub |
Gotcha! |
Pull Request Description
This PR adds a new GitHub workflow that automatically builds nightly/general release builds for Android. I've opted to only work on the automated Android build for now as iOS requires a bit more effort to get set up (in particular, I would need to generate new provisioning profiles and certificates to perform automatic builds)
With the Android automated builds, I'll also be able to (hopefully) finalize the requirements needed for F-Droid reproducible builds. Once this PR is merged and a new nightly is built, I'll be able to verify that the F-Droid build process works as intended.
The next step after automating Android builds is to generate a template release markdown file to automatically populate the release notes!
Issue Being Fixed
Issue Number: N/A
Screenshots / Recordings
Checklist
semanticLabel
s where applicable for accessibility?